← Back to issue list

The base field created by snapcraft init should match the docker equivalent image or raise an error

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1830388
Type
issue
State
open
Author
~ev
Labels
Created
2019-05-24 14:26:40.127289+00:00
Updated
2019-05-24 14:43:12.968116+00:00
Closed

Current evaluation

No evaluation has been recorded for this issue yet.

Issue body

(See also https://bugs.launchpad.net/snapcraft/+bug/1830389) Running snapcraft init inside the 16.04 snapcore/snapcraft docker produces a snapcraft.yaml with base: core18. You'll likely add some *-packages and this will break. Snapcraft init should select base: core if inside a 16.04 Docker, base: core18 if in 18.04 Docker, or error otherwise. It may be worth moving the snapcore/snapcraft:latest, :beta, and :candidate images to 18.04 (but worth weighing the impact to existing users). ~/example❯ docker run -v $(pwd):$(pwd) -w $(pwd) snapcore/snapcraft:beta snapcraft init Locale not set! Snapcraft will temporarily use C.UTF-8 Created snap/snapcraft.yaml. Go to https://docs.snapcraft.io/the-snapcraft-format/8337 for more information about the snapcraft.yaml format. ~/example❯ cat snap/snapcraft.yaml name: my-snap-name # you probably want to 'snapcraft register <name>' base: core18 # the base snap is the execution environment for this snap version: '0.1' # just for humans, typically '1.2+git' or '1.3.2' summary: Single-line elevator pitch for your amazing snap # 79 char long summary description: |   This is my-snap's description. You have a paragraph or two to tell the   most important story about your snap. Keep it under 100 words though,   we live in tweetspace and your description wants to look good in the snap   store. grade: devel # must be 'stable' to release into candidate/stable channels confinement: devmode # use 'strict' once you have the right plugs and slots parts:   my-part:     # See 'snapcraft plugins'     plugin: nil

Evaluation history

No evaluation history available.